Description

Story: https://labelbox.atlassian.net/browse/PLT-1701

This PR integrates the lbox workflow into our SDK build process, enabling automatic publishing of new lbox libraries with SDK releases.

Goals Not Achieved: Hard-coded library names remain in the provenance step of the lbox workflow.

Discussion: We're using the third-party reusable GitHub workflow slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@v2.0.0. In GitHub Actions, reusable workflows run as separate jobs, not steps within a job.

To dynamically build multiple lbox libraries, we need a matrix with dynamic entries. If we could run the provenance workflow as a job step, it would support a dynamic package matrix. However, this isn’t possible with the current setup.

Links:

• Github reusing workflows: https://docs.github.com/en/actions/sharing-automations/reusing-workflows#calling-a-reusable-workflow
  -Possible workaround path: https://github.com/orgs/community/discussions/17245 or https://github.com/marketplace/actions/matrix-outputs-write
• Programatically generate a new matrix (write a custom filter)

We do not have 2 lbox packages atm, so the flow will work as is. I will revisit at the end of sprint if I have time

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Document change (fix typo or modifying any markdown files, code comments or anything in the examples folder only)

All Submissions

• Have you followed the guidelines in our Contributing document?
• Have you provided a description?
• Are your changes properly formatted?

New Feature Submissions

• Does your submission pass tests?
• Have you added thorough tests for your new feature?
• Have you commented your code, particularly in hard-to-understand areas?
• Have you added a Docstring?

Changes to Core Features

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?
• Have you updated any code comments, as applicable?